You can launch application workloads from IEC marketplace or from scratch by manually creating a workload from EonKube > Advanced > Workloads. When creating a new workload, you need to consider and configure the following according to your application:

1. Workload type: Choose the appropriate workload type according to the requirements of your application:
   • Deployments: Deployments are suitable for stateless applications such as web services or API servers. Deployment supports rolling updates and automatic expansion, allowing users to gradually update each instance of the application without affecting the service. Through Deployment, you can easily manage application upgrades and rollbacks to ensure application stability.
   • StatefulSets: For a stateful application, such as a database or a distributed application, StatefulSet provides persistent storage and orderly startup capabilities. Each instance (pod) has a fixed identity (persistent identifier) and storage volume to ensure the stability and consistency of data. This is especially important if application state needs to be preserved.
   • DaemonSet: DaemonSet ensures that one application instance is running on each node, and is usually used for system-level applications, such as log collectors, monitoring agents, and network services. When a new node joins the cluster, DaemonSet will automatically deploy corresponding application instances on the new node to ensure that all nodes have the same service capabilities.
   • Jobs: Jobs are used to perform one-time tasks such as data processing, backup, or report generation. The job will automatically terminate after the task is completed to ensure that resources are not wasted. You can set the execution conditions, the number of retries, and the criteria of the Job completion.
   • CronJobs: CronJob is a time-based Job suitable for regularly-performed tasks, such as data backup at midnight every day or generating reports every week. CronJob provides flexible time scheduling configuration. You can set certain execution time and frequency to ensure that tasks are completed on time.
   • Pods: Pods are the smallest units of computing that you can create and manage in Kubernetes. A pod is a group of one or more containers, with shared storage and network resources, and a specification for how to run the containers.
2. Basic configurations: Specify the application name, namespace, container image, environment variables, storage, network settings, and node scheduling.
   • Pod replicas and update strategy: Set the required number of Pod replicas and configure an upgrade strategy of rolling update or re-creation.
   • Resource limit: Set CPU and memory resource quotas for each Pod to ensure that the computing resources can support the workloads run continuously.
   • Security policy: Configure security context, e.g. allowed users, file system permissions, network policies, etc.

After deployment, the application will automatically run on the specified node. For the network settings of a workload, see Expose a Workload as a Service. For more information about deploying a workload, see below deployment examples.